Skip to content

[XM Cyber] Add XM Cyber integration - #20043

Merged
efd6 merged 3 commits into
elastic:mainfrom
muskan-agarwal26:xm_cyber-0.1.0
Jul 9, 2026
Merged

efd6 merged 3 commits into
elastic:mainfrom
muskan-agarwal26:xm_cyber-0.1.0

Conversation

@muskan-agarwal26

@muskan-agarwal26 muskan-agarwal26 commented Jul 8, 2026 •

Copy link
Copy Markdown
Contributor

Proposed commit message

This PR adds the XM Cyber integration, including the audit_trail, device, entity_inventory, product, risk_score, and vulnerability data streams, along with their associated dashboards and visualizations.

XM Cyber fields are mapped to their corresponding ECS fields where possible.

Test samples were derived from live data samples, which were subsequently sanitized.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

How to test this PR locally

To test the XM Cyber package:

  • Clone integrations repo.
  • Install elastic package locally.
  • Start elastic stack using elastic-package.
  • Move to integrations/packages/xm_cyber directory.
  • Run the following command to run tests.

elastic-package test

Run asset tests for the package
2026/07/08 23:31:34  INFO elastic-package v0.125.1 version-hash 111636ab (build time: 2026-07-03T17:56:06+05:30)
2026/07/08 23:31:34  INFO elastic-stack: 8.18.0
2026/07/08 23:31:34  INFO License text found in "/root/elastic/github/integrations/LICENSE.txt" will be included in package
--- Test results for package: xm_cyber - START ---
╭──────────┬──────────────────┬───────────┬───────────────────────────────────────────────────────────────────┬────────┬──────────────╮
│ PACKAGE  │ DATA STREAM      │ TEST TYPE │ TEST NAME                                                         │ RESULT │ TIME ELAPSED │
├──────────┼──────────────────┼───────────┼───────────────────────────────────────────────────────────────────┼────────┼──────────────┤
│ xm_cyber │                  │ asset     │ dashboard xm_cyber-2170babe-e0a3-4289-a13b-fcb606f812a7 is loaded │ PASS   │      2.086µs │
│ xm_cyber │                  │ asset     │ dashboard xm_cyber-73ae0dbf-0f50-4183-8f0a-6489ca47f1d6 is loaded │ PASS   │        258ns │
│ xm_cyber │                  │ asset     │ dashboard xm_cyber-8591539b-edd7-42bb-bfa0-2ea26a334900 is loaded │ PASS   │        219ns │
│ xm_cyber │                  │ asset     │ dashboard xm_cyber-96451398-d474-49d3-b76a-f328996127dd is loaded │ PASS   │        186ns │
│ xm_cyber │                  │ asset     │ dashboard xm_cyber-cbb01e78-83e3-4470-8047-209335be7d65 is loaded │ PASS   │        179ns │
│ xm_cyber │                  │ asset     │ dashboard xm_cyber-e671cff1-1a11-4326-a51d-04b32831df5b is loaded │ PASS   │        185ns │
│ xm_cyber │                  │ asset     │ search xm_cyber-32f648df-d7e1-4757-af30-edf43a9a1299 is loaded    │ PASS   │        272ns │
│ xm_cyber │ audit_trail      │ asset     │ index_template logs-xm_cyber.audit_trail is loaded                │ PASS   │        270ns │
│ xm_cyber │ audit_trail      │ asset     │ ingest_pipeline logs-xm_cyber.audit_trail-0.1.0 is loaded         │ PASS   │        110ns │
│ xm_cyber │ device           │ asset     │ index_template logs-xm_cyber.device is loaded                     │ PASS   │        438ns │
│ xm_cyber │ device           │ asset     │ ingest_pipeline logs-xm_cyber.device-0.1.0 is loaded              │ PASS   │         99ns │
│ xm_cyber │ entity_inventory │ asset     │ index_template logs-xm_cyber.entity_inventory is loaded           │ PASS   │        166ns │
│ xm_cyber │ entity_inventory │ asset     │ ingest_pipeline logs-xm_cyber.entity_inventory-0.1.0 is loaded    │ PASS   │        140ns │
│ xm_cyber │ product          │ asset     │ index_template logs-xm_cyber.product is loaded                    │ PASS   │        286ns │
│ xm_cyber │ product          │ asset     │ ingest_pipeline logs-xm_cyber.product-0.1.0 is loaded             │ PASS   │        163ns │
│ xm_cyber │ risk_score       │ asset     │ index_template logs-xm_cyber.risk_score is loaded                 │ PASS   │        230ns │
│ xm_cyber │ risk_score       │ asset     │ ingest_pipeline logs-xm_cyber.risk_score-0.1.0 is loaded          │ PASS   │        124ns │
│ xm_cyber │ vulnerability    │ asset     │ index_template logs-xm_cyber.vulnerability is loaded              │ PASS   │        146ns │
│ xm_cyber │ vulnerability    │ asset     │ ingest_pipeline logs-xm_cyber.vulnerability-0.1.0 is loaded       │ PASS   │        166ns │
╰──────────┴──────────────────┴───────────┴───────────────────────────────────────────────────────────────────┴────────┴──────────────╯
--- Test results for package: xm_cyber - END   ---
Done
Run pipeline tests for the package
2026/07/08 23:31:43  INFO elastic-package v0.125.1 version-hash 111636ab (build time: 2026-07-03T17:56:06+05:30)
2026/07/08 23:31:43  INFO elastic-stack: 8.18.0
--- Test results for package: xm_cyber - START ---
╭──────────┬──────────────────┬───────────┬──────────────────────────────────────────────────────┬────────┬──────────────╮
│ PACKAGE  │ DATA STREAM      │ TEST TYPE │ TEST NAME                                            │ RESULT │ TIME ELAPSED │
├──────────┼──────────────────┼───────────┼──────────────────────────────────────────────────────┼────────┼──────────────┤
│ xm_cyber │ audit_trail      │ pipeline  │ (ingest pipeline warnings test-audit-trail.log)      │ PASS   │ 398.417166ms │
│ xm_cyber │ audit_trail      │ pipeline  │ test-audit-trail.log                                 │ PASS   │ 412.485928ms │
│ xm_cyber │ device           │ pipeline  │ (ingest pipeline warnings test-device.log)           │ PASS   │ 294.299242ms │
│ xm_cyber │ device           │ pipeline  │ test-device.log                                      │ PASS   │ 243.608103ms │
│ xm_cyber │ entity_inventory │ pipeline  │ (ingest pipeline warnings test-entity-inventory.log) │ PASS   │ 341.937227ms │
│ xm_cyber │ entity_inventory │ pipeline  │ test-entity-inventory.log                            │ PASS   │  300.28723ms │
│ xm_cyber │ product          │ pipeline  │ (ingest pipeline warnings test-product.log)          │ PASS   │ 324.556305ms │
│ xm_cyber │ product          │ pipeline  │ test-product.log                                     │ PASS   │ 154.548466ms │
│ xm_cyber │ risk_score       │ pipeline  │ (ingest pipeline warnings test-risk-score.log)       │ PASS   │ 310.962073ms │
│ xm_cyber │ risk_score       │ pipeline  │ test-risk-score.log                                  │ PASS   │ 163.643001ms │
│ xm_cyber │ vulnerability    │ pipeline  │ (ingest pipeline warnings test-vulnerability.log)    │ PASS   │ 282.657768ms │
│ xm_cyber │ vulnerability    │ pipeline  │ test-vulnerability.log                               │ PASS   │ 245.685106ms │
╰──────────┴──────────────────┴───────────┴──────────────────────────────────────────────────────┴────────┴──────────────╯
--- Test results for package: xm_cyber - END   ---
Done
Run policy tests for the package
2026/07/08 23:31:47  INFO elastic-package v0.125.1 version-hash 111636ab (build time: 2026-07-03T17:56:06+05:30)
2026/07/08 23:31:47  INFO elastic-stack: 8.18.0
--- Test results for package: xm_cyber - START ---
No test results
--- Test results for package: xm_cyber - END   ---
Done
Run script tests for the package
PKG xm_cyber
[no test files]
--- Test results for package: xm_cyber - START ---
No test results
--- Test results for package: xm_cyber - END   ---
Done
Run static tests for the package
2026/07/08 23:31:48  INFO elastic-package v0.125.1 version-hash 111636ab (build time: 2026-07-03T17:56:06+05:30)
--- Test results for package: xm_cyber - START ---
╭──────────┬──────────────────┬───────────┬──────────────────────────┬────────┬──────────────╮
│ PACKAGE  │ DATA STREAM      │ TEST TYPE │ TEST NAME                │ RESULT │ TIME ELAPSED │
├──────────┼──────────────────┼───────────┼──────────────────────────┼────────┼──────────────┤
│ xm_cyber │ audit_trail      │ static    │ Verify sample_event.json │ PASS   │ 195.050869ms │
│ xm_cyber │ device           │ static    │ Verify sample_event.json │ PASS   │ 162.894752ms │
│ xm_cyber │ entity_inventory │ static    │ Verify sample_event.json │ PASS   │ 166.905013ms │
│ xm_cyber │ product          │ static    │ Verify sample_event.json │ PASS   │  140.67051ms │
│ xm_cyber │ risk_score       │ static    │ Verify sample_event.json │ PASS   │ 137.109906ms │
│ xm_cyber │ vulnerability    │ static    │ Verify sample_event.json │ PASS   │ 154.546336ms │
╰──────────┴──────────────────┴───────────┴──────────────────────────┴────────┴──────────────╯
--- Test results for package: xm_cyber - END   ---
Done
Run system tests for the package
2026/07/08 23:31:49  INFO elastic-package v0.125.1 version-hash 111636ab (build time: 2026-07-03T17:56:06+05:30)
2026/07/08 23:31:49  INFO elastic-stack: 8.18.0
2026/07/08 23:31:49  INFO Installing package...
2026/07/08 23:31:49  INFO License text found in "/root/elastic/github/integrations/LICENSE.txt" will be included in package
2026/07/08 23:31:52  INFO Running test for data_stream "audit_trail" with configuration 'default'
2026/07/08 23:32:01  INFO Setting up independent Elastic Agent...
2026/07/08 23:32:16  INFO Setting up service...
2026/07/08 23:32:35  INFO Validating test case...
2026/07/08 23:32:36  INFO Tearing down service...
2026/07/08 23:32:36  INFO Write container logs to file: /root/elastic/github/integrations/build/container-logs/xm_cyber-1783533756705831317.log
2026/07/08 23:32:38  INFO Tearing down agent...
2026/07/08 23:32:39  INFO Write container logs to file: /root/elastic/github/integrations/build/container-logs/elastic-agent-1783533759013850615.log
2026/07/08 23:32:48  INFO Running test for data_stream "device" with configuration 'default'
2026/07/08 23:32:56  INFO Setting up independent Elastic Agent...
2026/07/08 23:33:06  INFO Setting up service...
2026/07/08 23:33:21  INFO Validating test case...
2026/07/08 23:33:21  INFO Tearing down service...
2026/07/08 23:33:22  INFO Write container logs to file: /root/elastic/github/integrations/build/container-logs/xm_cyber-1783533802102998078.log
2026/07/08 23:33:23  INFO Tearing down agent...
2026/07/08 23:33:24  INFO Write container logs to file: /root/elastic/github/integrations/build/container-logs/elastic-agent-1783533804038030884.log
2026/07/08 23:33:33  INFO Running test for data_stream "entity_inventory" with configuration 'default'
2026/07/08 23:33:41  INFO Setting up independent Elastic Agent...
2026/07/08 23:33:56  INFO Setting up service...
2026/07/08 23:34:15  INFO Validating test case...
2026/07/08 23:34:15  INFO Tearing down service...
2026/07/08 23:34:16  INFO Write container logs to file: /root/elastic/github/integrations/build/container-logs/xm_cyber-1783533856401109887.log
2026/07/08 23:34:17  INFO Tearing down agent...
2026/07/08 23:34:18  INFO Write container logs to file: /root/elastic/github/integrations/build/container-logs/elastic-agent-1783533858039614821.log
2026/07/08 23:34:24  INFO Running test for data_stream "product" with configuration 'default'
2026/07/08 23:34:30  INFO Setting up independent Elastic Agent...
2026/07/08 23:34:37  INFO Setting up service...
2026/07/08 23:34:59  INFO Validating test case...
2026/07/08 23:34:59  INFO Tearing down service...
2026/07/08 23:35:00  INFO Write container logs to file: /root/elastic/github/integrations/build/container-logs/xm_cyber-1783533900156386936.log
2026/07/08 23:35:01  INFO Tearing down agent...
2026/07/08 23:35:02  INFO Write container logs to file: /root/elastic/github/integrations/build/container-logs/elastic-agent-1783533902064889137.log
2026/07/08 23:35:08  INFO Running test for data_stream "risk_score" with configuration 'default'
2026/07/08 23:35:14  INFO Setting up independent Elastic Agent...
2026/07/08 23:35:26  INFO Setting up service...
2026/07/08 23:35:49  INFO Validating test case...
2026/07/08 23:35:49  INFO Tearing down service...
2026/07/08 23:35:50  INFO Write container logs to file: /root/elastic/github/integrations/build/container-logs/xm_cyber-1783533950342360268.log
2026/07/08 23:35:51  INFO Tearing down agent...
2026/07/08 23:35:52  INFO Write container logs to file: /root/elastic/github/integrations/build/container-logs/elastic-agent-1783533952081387286.log
2026/07/08 23:35:59  INFO Running test for data_stream "vulnerability" with configuration 'default'
2026/07/08 23:36:06  INFO Setting up independent Elastic Agent...
2026/07/08 23:36:16  INFO Setting up service...
2026/07/08 23:36:34  INFO Validating test case...
2026/07/08 23:36:35  INFO Tearing down service...
2026/07/08 23:36:35  INFO Write container logs to file: /root/elastic/github/integrations/build/container-logs/xm_cyber-1783533995633423472.log
2026/07/08 23:36:37  INFO Tearing down agent...
2026/07/08 23:36:38  INFO Write container logs to file: /root/elastic/github/integrations/build/container-logs/elastic-agent-1783533998098860213.log
2026/07/08 23:36:46  INFO Uninstalling package...
--- Test results for package: xm_cyber - START ---
╭──────────┬──────────────────┬───────────┬───────────┬────────┬───────────────╮
│ PACKAGE  │ DATA STREAM      │ TEST TYPE │ TEST NAME │ RESULT │  TIME ELAPSED │
├──────────┼──────────────────┼───────────┼───────────┼────────┼───────────────┤
│ xm_cyber │ audit_trail      │ system    │ default   │ PASS   │ 43.611566174s │
│ xm_cyber │ device           │ system    │ default   │ PASS   │ 33.394395923s │
│ xm_cyber │ entity_inventory │ system    │ default   │ PASS   │ 42.723381153s │
│ xm_cyber │ product          │ system    │ default   │ PASS   │ 35.302965635s │
│ xm_cyber │ risk_score       │ system    │ default   │ PASS   │ 41.562892966s │
│ xm_cyber │ vulnerability    │ system    │ default   │ PASS   │ 35.814043757s │
╰──────────┴──────────────────┴───────────┴───────────┴────────┴───────────────╯
--- Test results for package: xm_cyber - END   ---
Done

Related issues

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

github-actions Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs Style Checker (Vale)

Summary: 267 warnings, 13 suggestions found

⚠️ Warnings (267): Fix when the suggestion improves clarity or correctness.
File Line Rule Message
packages/xm_cyber/_dev/build/docs/README.md 98 Elastic.DirectionalLanguage Don't use directional language. Use 'the following element' instead of 'the table below'.
packages/xm_cyber/data_stream/audit_trail/manifest.yml 34 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/device/fields/fields.yml 4 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/device/fields/fields.yml 55 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/device/fields/fields.yml 133 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/device/manifest.yml 34 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 18 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 63 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 153 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 162 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 183 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 201 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 216 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 219 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 225 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 261 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 270 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 285 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 417 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 420 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 423 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 426 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 429 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 432 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 435 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 438 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 441 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 444 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 450 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 453 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 453 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 453 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 453 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 453 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 453 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 453 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 456 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 459 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 462 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 465 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 468 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 471 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 474 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 477 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 480 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 483 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 486 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 489 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 492 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 495 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 498 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 501 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 504 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 507 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 510 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 513 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 516 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 519 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 522 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 528 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 531 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 534 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 537 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 540 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 543 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 546 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 549 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 552 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 555 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 558 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 561 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 564 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 567 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 570 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 573 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 576 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 579 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 582 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 585 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 588 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 591 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 597 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 600 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 603 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 609 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 612 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 615 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 618 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 621 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 624 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 627 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 633 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 636 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 639 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 642 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 645 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 648 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 651 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 654 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 657 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 660 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 663 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 666 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 669 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 672 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 675 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 678 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 681 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 684 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 687 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 690 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 693 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 696 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 699 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 702 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 705 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 708 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 711 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 714 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 717 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 720 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 723 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 726 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 729 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 732 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 735 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 738 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 741 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 744 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 747 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 750 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 753 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 756 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 759 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 762 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 765 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 768 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 771 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 774 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 777 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 780 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 783 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 786 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 789 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 792 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 795 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 798 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 801 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 804 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 807 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 807 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 807 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 810 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 813 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 816 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 819 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 822 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 825 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 828 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 831 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 834 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 837 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 843 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 846 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 849 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 852 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 855 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 858 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 861 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 864 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 870 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 873 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 876 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 879 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 882 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 885 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 888 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 891 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 894 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 897 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 900 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 903 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 906 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 909 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 912 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 915 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 918 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 921 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 924 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 927 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 930 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 933 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 936 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 939 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 945 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 948 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 951 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 954 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 957 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 960 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 963 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 966 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 969 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 972 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 975 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 978 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 981 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 987 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 990 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 993 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 996 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 999 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1002 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1005 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1008 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1011 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1014 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1017 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1020 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1023 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1029 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1032 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1035 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1038 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1041 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1044 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1047 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1050 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1050 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1053 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1062 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1065 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1068 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1074 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1080 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1083 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1086 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1089 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1092 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1095 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1098 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1101 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1104 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1107 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1110 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1113 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1116 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1119 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1122 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1125 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1128 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1134 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1137 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1140 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1143 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1146 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1149 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 1152 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/entity_inventory/manifest.yml 34 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/product/manifest.yml 34 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/risk_score/manifest.yml 46 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/data_stream/vulnerability/fields/fields.yml 7 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
packages/xm_cyber/data_stream/vulnerability/manifest.yml 35 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/manifest.yml 64 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/xm_cyber/manifest.yml 77 Elastic.DontUse Don't use 'Please'.
packages/xm_cyber/manifest.yml 83 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'that is' instead of 'i.e'.
packages/xm_cyber/manifest.yml 83 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
💡 Suggestions (13): Optional style improvements. Apply when helpful.
File Line Rule Message
packages/xm_cyber/changelog.yml 1 Elastic.Versions Use 'later versions' instead of 'newer versions' when referring to versions.
packages/xm_cyber/data_stream/device/fields/fields.yml 112 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/xm_cyber/data_stream/device/fields/fields.yml 133 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 118 Elastic.WordChoice Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 120 Elastic.WordChoice Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 121 Elastic.WordChoice Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 123 Elastic.WordChoice Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 435 Elastic.WordChoice Consider using 'start, run' instead of 'Boot', unless the term is in the UI.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 570 Elastic.Repetition "volume" is repeated.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 672 Elastic.Repetition "cache" is repeated.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 828 Elastic.WordChoice Consider using 'open' instead of 'Launch', unless the term is in the UI.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 831 Elastic.WordChoice Consider using 'open' instead of 'Launch', unless the term is in the UI.
packages/xm_cyber/data_stream/entity_inventory/fields/fields.yml 900 Elastic.Repetition "cluster" is repeated.

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@muskan-agarwal26
muskan-agarwal26 marked this pull request as ready for review July 8, 2026 17:54
@muskan-agarwal26
muskan-agarwal26 requested a review from a team as a code owner July 8, 2026 17:54
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Changelog link mismatch — expected https://github.com/elastic/integrations/pull/20043 in the following file(s):

  • packages/xm_cyber/changelog.yml

Tip

If expected, add the changelog-link-check:skip label to skip this check. Or, if an issue link was intended, use .../issues/<n> instead.

View Buildkite build
@muskan-agarwal26

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@andrewkroh andrewkroh added documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. Crest Contributions from Crest developement team. New Integration Issue or pull request for creating a new integration package. labels Jul 8, 2026
@efd6

efd6 commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

/test

@efd6 efd6 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comes from 1. feature/xm_cyber-0.1.0 (at 15dbac1) and is a squash of that, then 2. the changelog update, and then 3. the merge of main back in.

@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

💚 Build Succeeded

History

@mergify

mergify Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request

@efd6
efd6 merged commit 53c7432 into elastic:main Jul 9, 2026
12 checks passed
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Package xm_cyber - 0.1.0 containing this change is available at https://epr.elastic.co/package/xm_cyber/0.1.0/

@andrewkroh andrewkroh added dashboard Relates to a Kibana dashboard bug, enhancement, or modification. Integration:xm_cyber XM Cyber labels Jul 9, 2026
@kcreddy

kcreddy commented Jul 22, 2026 •

Copy link
Copy Markdown
Contributor

@muskan-agarwal26, @piyush-elastic
Looks like most new integrations are missing @elastic/sit-crest-contractors from the CODEOWNERS. Can you please add them going forward?

/packages/xm_cyber @elastic/security-service-integrations

Adding for the missed ones here: #20277

cc: @efd6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog-link-check:skip Crest Contributions from Crest developement team. dashboard Relates to a Kibana dashboard bug, enhancement, or modification. documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. Integration:xm_cyber XM Cyber New Integration Issue or pull request for creating a new integration package.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants